home *** CD-ROM | disk | FTP | other *** search
- Path: in1.uu.net!tandem!usenet
- From: Anatoli Mandelchtam <tolik@tarley_pc.loc201.tandem.com>
- Newsgroups: comp.lang.c++
- Subject: Re: Need help reading sockets
- Date: Sun, 24 Mar 1996 22:34:13 -0800
- Organization: Tandem Computers Inc., Cupertino, CA
- Message-ID: <31563E65.74B1@tarley_pc.loc201.tandem.com>
- References: <4j23rh$bnu@ginger.lei.net>
- NNTP-Posting-Host: miket_home1.fnord.tandem.com
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 2.01 (Win95; I)
-
- Daniel Nakamura wrote:
- .>
- .> I have a problem with reading sockets. I'm currently using the read
- .> function to read sockets, then put the information into a buffer. The
- .> problem is that I can't read the socket until there is a cariage return.
- .> I'd like to read the socket character by character instead of waiting for
- .> the charage return. Does anyone know how to do it?
-
- Strange. I always thought that one reads sockets in buffers and buffer length
- mostly depends on how application on the other side writes into its the socket.
-
- Could you be more specific describing your problem, please?
-
- Regards,
-
- Anatoli.
-